@ArnobKumarSaha @groundnuty can you please review and merge it?

@groundnuty Mind merging this in to address security vulnerabilities?

@spideyfusion k8s-wait-for will be updated in December and after that, I plan to do a release every ~6 months.

@spideyfusion @ashutoshrathore I'm updating the dependencies and releasing the new version this week, but this constant race against vulnerabilities is too rapid for a biannual release cycle.

I researched using https://www.chainguard.dev images as they seem to be popular nowadays in devops circles.
My intention was to use their kubectl and reguild k8s-wait-for image with github workflows eg. weekly with pined kubectl version and updated dependences, but last year they disabled pulling images with any version but latest...

Do you have any recommendations/know the best practices on how to tackle the problem of vulnerability fixes in an automatic manner, but still maintaining stability of the tool?